System and method of wireless downloads of map and geographic based data to portable computing devices

ABSTRACT

Systems and methods of managing map data on electronic devices are disclosed. In one aspect, a method of downloading pushpin data for a map is disclosed. The method includes receiving, from an electronic network, an indication of a current map segment, the current map segment comprising map data for a current location of a device, the current map segment corresponding to a portion of a map displayed on the device, receiving pushpin criteria for the device, identifying pushpin data based on the current map segment and the pushpin criteria, the pushpin data indicating a pushpin location; and transmitting, on the electronic network, the pushpin data.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.13/464,654, filed May 4, 2012 (now U.S. Pat. No. 8,649,968), which is acontinuation of U.S. patent application Ser. No. 13/185,052, filed Jul.18, 2011 (now U.S. Pat. No. 8,195,389), which is a continuation of U.S.patent application Ser. No. 12/543,305, filed Aug. 18, 2009 (now U.S.Pat. No. 8,014,945), which is a continuation of U.S. patent applicationSer. No. 11/222,208, filed Sep. 7, 2005 (now abandoned), which claimsthe benefit of U.S. Provisional Application No. 60/607,895, filed Sep.7, 2004 and U.S. Provisional Application No. 60/627,393, filed Nov. 12,2004. Each of the aforementioned applications is incorporated byreference in its entirety.

FIELD OF THE INVENTION

The invention relates to management of map data and geographicallyrelated content on an electronic device. In addition, the inventionrelates to sending and receiving map data from and to a mobileelectronic device.

BACKGROUND OF THE INVENTION

A variety of electronic devices, such as mobile computers, mobilewireless telephones, global positioning system (GPS) units, personaldigital assistants (PDAs), or automobile navigation systems, may providemap display and storage capabilities. In addition, some electronicdevices also include software for storing address books, email, Internetbrowsing, or other applications that generate or organize map data andgeographically related content. The term “geographically relatedcontent” may refer to any information, e.g., related to a person, place,or object, that has associated geographic references. A “geographicreference” may include a street address, city, zip code, postal code,municipality, region, county, state, province, country, coordinate,latitude, longitude, pseudo-coordinate or geographic index number.

However, a need exists for improved systems and methods of integratingbetween the map and geographically related content display and storagecapabilities of these devices and other software on the devices.Moreover, a need exists for improved systems and methods ofcommunicating, or downloading, map data and geographically relatedcontent to and from such devices.

SUMMARY OF THE INVENTION

The system, method, and devices of the invention each have severalaspects, no single one of which is solely responsible for its desirableattributes. Without limiting the scope of this invention, some of itsmore prominent features will now be discussed briefly. After consideringthis discussion, and particularly after reading the section entitled“Detailed Description of Certain Inventive Embodiments” one willunderstand how the features of this invention provide advantages thatinclude sharing of geographically related data.

One embodiment is a method of processing geographically referencedcontent comprising geographical coordinate data in a portable computingdevice. The method includes receiving, from a first source,geographically referenced content comprising geographic coordinate data.The method further includes receiving a geographic map from a secondsource. The method further includes storing the received, geographicallyreferenced content in a first portion the data storage. The methodfurther includes storing the geographical map in a second portion of thedata storage. The method further includes retrieving the geographicalmap from the second portion of the data storage based at least in parton a geographical index of the geographical map. The method furtherincludes retrieving geographically referenced content from the firstportion of the data storage based at least in part on a geographicalindex of the geographically referenced content. The method furtherincludes displaying the geographical map on a visual display. The methodfurther includes displaying an icon on the displayed geographical map.The location of the icon on the geographical map corresponds to thegeographical coordinate data of the retrieved geographically referencedcontent.

Another embodiment includes a system for processing geographicallyreferenced content. The system includes means for receiving, from afirst source, geographically referenced content comprising geographiccoordinate data. The system further includes means for receiving ageographic map from a second source. The system further includes meansfor storing the received geographically referenced content. The systemfurther includes means storing the geographical map. The system furtherincludes means for retrieving the geographical map from the secondportion of the storing means based at least in part on a geographicalindex of the geographical map. The system further includes means forretrieving geographically referenced content from the storing meansbased at least in part on a geographical index of the geographicallyreferenced content. The system further includes means for displaying thegeographical map and displaying an icon on the displayed geographicalmap. The location of the icon on the geographical map corresponds to thegeographical coordinate data of the retrieved geographically referencedcontent.

Another embodiment includes a system for processing geographicallyreferenced content. The system includes at least one transceiverconfigured to receive, from a first source, geographically referencedcontent comprising geographic coordinate data and receive a geographicmap from a second source. The system further includes at least onestorage configured to store the received geographically referencedcontent and store the geographical map. The system further includes aprocessor configured to retrieve the geographical map from the secondportion of the storage based at least in part on a geographical index ofthe geographical map, and retrieve geographically referenced contentfrom the storage based at least in part on a geographical index of thegeographically referenced content. The system further includes a displayconfigured to display the geographical map and to display an icon on thedisplayed geographical map. The location of the icon on the geographicalmap corresponds to the geographical coordinate data of the retrievedgeographically referenced content.

Another embodiment includes a method of sharing geographicallyreferenced content. The method includes receiving geographicallyreferenced content from a first mobile electronic device for a secondmobile electronic device. Each of the first and second mobile electronicdevices comprises a wireless communications transceiver. The methodfurther includes sending data identifying the received geographicallyreferenced content to the second mobile electronic device. The methodfurther includes processing a request from the second mobile electronicdevice for the received geographically referenced content. The methodfurther includes sending the received geographically referenced contentto the second mobile electronic device in response to the request fromthe second mobile electronic device.

Another embodiment includes a network for transmitting data. The networkincludes a first communications link configured to communicategeographically referenced content between a first and second wirelessdevice. The network further includes a second communications linkconfigured to communicate the geographically referenced content betweenthe second wireless device and a third wireless device. Thegeographically referenced content comprises geographic coordinate dataof a location which is adapted to be selectively displayed as an icon ona map.

Another embodiment includes a method of sharing geographicallyreferenced content. The method includes receiving a request forgeographically referenced content from a first mobile electronic deviceon a second mobile device. The method further includes determiningwhether the first mobile device is authorized to receive thegeographically referenced content. The method further includes sendingthe requested geographically referenced content to the first mobileelectronic device in response to the request.

Another embodiment includes a system for sharing geographicallyreferenced content, The system includes means for communicating with asecond mobile electronic device, means for processing comprising meansfor receiving a request for geographically referenced content from thesecond mobile electronic device, means for determining whether the firstmobile electronic device is authorized to receive the geographicallyreferenced content, and means for the received geographically referencedcontent to the first mobile electronic device in response to therequest.

Another embodiment includes a method of caching map data. The methodincludes storing a plurality of map segments in a cache. The methodfurther includes associating each of the map segments with a rank. Themethod further includes updating the rank of at least one of the mapsegments when the at least one map segment is accessed. The methodfurther includes selecting at least one map segment from the cache to beremoved based at least in part on the rank of the at least one selectedmap segment. The method further includes removing the at least oneselected map segment from the cache.

Another embodiment includes system for displaying map data. The systemincludes means for identifying each of a plurality of geographicallyreferenced contents with an index that is determined based at least inpart on geographic coordinates of the respective geographicallyreferenced content, means for displaying a representation of a mapcomprising a plurality of map segments at a selected zoom level on adisplay, means for comparing the index of each of the geographicallyreferenced contents to respective indices associated with each of theplurality of map segments, means for selecting at least one of thegeographically referenced contents based at least in part on results ofthe comparing, and means for displaying the at least one of thegeographically referenced contents on the display.

Another embodiment includes a method of storing map segments. The methodincludes storing at least one first map segment representing ageographic area at a first zoom level in a storage. The method furtherincludes storing at least one map segment representing a portion of thegeographic area at a second zoom level in the storage. The methodfurther includes displaying the first segment on a display. The methodfUrther includes visually representing the portion of the geographicarea represented by the at least one stored map segment on the display.The at least one stored map segment is visually represented differentlyon the display from portions of the geographic area that correspond tomap segments at the second zoom level that are absent from the storage.

Another embodiment includes a device for storing and displaying mapdata. The device includes a storage configure to store at least onefirst map segment representing a geographic area at a first zoom leveland configured to store at least one map segment representing a portionof the geographic area at a second zoom level. The device furtherincludes a display configured to display at least the at least one firstsegment and to visually represent the portion of the geographic arearepresented by the at least one stored map segment, wherein the at leastone stored map segment is visually represented differently on thedisplay from portions of the geographic area that correspond to mapsegments at the second zoom level that are absent from the storage. Thedevice further includes a processor configured to control display of themap segments.

Another embodiment includes a method of accessing map data. The methodincludes receiving a selection of map data from a user interface. Themethod further includes storing data indicative of the selected map datain association with data indicative of how to display the map data. Thedata indicative of the map data comprises at least one of a zoom level,a map center location, and at least one map layer to display.

Another embodiment includes a method of accessing preferred maplocations. The method includes displaying a list of geographic regions.The method further includes displaying a list of types of geographicallyreferenced content. The method further includes receiving geographicallyreference content in one of the geographic regions corresponding to atleast one of the types of geographically referenced content. The methodfurther includes storing the geographically referenced content and thetype of geographically referenced content in association with the one ofthe geographic regions. The method further includes displaying a list ofgeographically referenced contents in the one of the geographic regions.The stored geographically referenced content is displayed differentlythan others of the geographically referenced contents.

Another embodiment includes a method of displaying labels associatedwith locations on a map comprising a plurality of map segments. Themethod includes ordering a plurality of locations based on respectiveranks of the locations. The method further includes selecting apredetermined number of the locations for display within each of theplurality of map segments based on the order of the ranked locations.The method further includes displaying the selected locations. Thepredetermined number of locations is based at least in part on the zoomlevel of the map segments.

Another embodiment includes a system for providing directions on anelectronic device. The system includes a display configured to display amap. The display is further configured to display a menu comprising aplurality of geographically referenced contents. The system furtherincludes a input device configured to receive activation of a userinterface control associated with at least one of the geographicallyreferenced contents. The system further includes a locatingdetermination device configured to determine a location of the system.The system further includes a processor configured to displaying”directions on the display between the location of the system and the atleast one of the geographically referenced contents associated with theactivated control.

Another embodiment includes a system for creating geographicallyreferenced content. The system includes means for receiving a selectionof displayed text comprising an address, means for identifyinggeographic coordinates associated with the address, means for generatinggeographically referenced contents associating the address with thegeographic coordinates, and means for storing the geographicallyreferenced contents.

Another embodiment includes system for identifying a portion of a map ona display. The system includes means for associating each of a pluralityof regions of the map with a different color, means for displaying eachof the regions on the display in the associated color, means forreceiving a user selection of a pixel of the display, means fordetermining the color of the pixel, and means for identifying a selectedregion of the map by identifying the color of the pixel with the colorassociated with the selected region.

Another embodiment includes a method of preloading map data. The methodincludes storing map data on an electronic device. The method furtherincludes determining the location of the electronic device. The methodfurther includes predicting a direction of travel of the electronicdevice. The method further includes identifying map data along thedirection of travel that is absent from the stored map data. The methodfurther includes receiving the identified map data along the predicteddirection of travel. The method further includes storing the identifiedmap data.

Another embodiment includes a system for preloading map data. The systemincludes a storage configured to store map data on an electronic device.The system further includes a device configured to determine thelocation of the electronic device. The system further includes atransceiver configured to receive map data. The system further includesa processor configured to identify a route of travel of the electronicdevice, identify map data along the route of travel that is absent fromthe stored map data, and download the identified map data along theroute of travel via the transceiver.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram depicting one embodiment of a networkedelectronic device.

FIG. 2 is a block diagram depicting software modules of one embodimentof a system for managing map data and geographically related content onan electronic device, such as the embodiment of an electronic devicedepicted in FIG. 1.

FIG. 3 is a schema diagram illustrating data formats of one embodimentof a system for managing map data and geographically related contentsuch as the system depicted in FIG. 2.

FIG. 4 is a flowchart illustrating one embodiment of a method ofcommunicating a pushpin between applications on the electronic device.

FIG. 5 is a flowchart illustrating one embodiment of a method ofcommunicating pushpin data directly between electronic devices.

FIGS. 6A-6C are display screen images from the source device 100illustrating exemplary views associated with entering pushpin data andsending the pushpin data to a destination device as illustrated by FIG.5.

FIG. 6D is a display screen image from the destination deviceillustrating exemplary views associated with receiving the pushpin dataon the destination device as also illustrated by FIG. 5.

FIG. 7 is a flowchart illustrating one embodiment of a method ofcommunicating pushpin data from an originating device to an intermediateserver.

FIG. 8 is a flowchart illustrating one embodiment of a method ofcommunicating pushpin data between electronic devices via theintermediate server.

FIG. 9 is a flowchart illustrating one embodiment of a method ofrequesting pushpin data from another electronic device.

FIG. 10 is a flowchart illustrating one embodiment of a method ofrequesting a pushpin from an intermediate server.

FIG. 11 is a flowchart illustrating one embodiment of a method ofrequesting pushpin data from another electronic device via anintermediate server.

FIG. 12 is a flow diagram illustrating a set of exemplary pushpincommands.

FIG. 13 is a flowchart further illustrating one embodiment of a methodof intelligently caching map segments.

FIG. 14A is a flowchart illustrating one embodiment of a method ofdetermining pushpin index numbers.

FIG. 14B is a flowchart illustrating one embodiment of a method ofdisplaying pushpins based on the pushpin index.

FIG. 15 is a flowchart illustrating one embodiment of a method ofdownloading pushpin data based on the pushpin index.

FIG. 16 is a screen shot illustrating exemplary views associated withone embodiment of the method of maintaining a cache of map segments.

FIG. 17 a is a flowchart illustrating one embodiment of method ofindicating the cache status of map segment data.

FIG. 17B is a flowchart illustrating another embodiment of a method ofmaintaining a cache of map data segments similar to the embodimentdepicted in FIG. 17A.

FIG. 17C is a flowchart illustrating a method of providing a userinterface for a user manually maintain a cache of map data.

FIGS. 18A-D are flowcharts that illustrate embodiments of methods ofmanipulating favorites.

FIG. 19A is a flowchart illustrating one embodiment of a method forcreating a list of preferred locations.

FIG. 19B is a screen shot illustrating exemplary views associated with agraphical user interface for selecting a particular region such as inthe embodiment of the method depicted in FIG. 19A.

FIG. 19C is a screen shot illustrating exemplary views associated with auser interface for selecting a preferred airport in that region.

FIG. 20A is flowchart illustrating one embodiment of a method ofencoding data to facilitate the display of location names based on thenumber of locations within the display area.

FIG. 20B is a flowchart illustrating one embodiment of a method ofdisplaying location names on a map based on the number of locationswithin the display area.

FIG. 21 is a flowchart illustrating an embodiment of a method ofproviding a user interface for getting driving directions from thecurrent location.

FIG. 22 is a flowchart illustrating one embodiment of a method forcreating a geocoded pushpin from text identified as containing anaddress.

FIG. 23A is a flowchart illustrating one embodiment of a method ofselecting colors for regions on a map.

FIG. 23B is a flowchart illustrating one embodiment of a method ofidentifying a selected region using a displayed map such as createdusing the method of FIG. 23A.

FIG. 24 is a flowchart illustrating an exemplary method of pre-cachingdata in a system such as illustrated in FIG. 1.

FIG. 25 is a flowchart illustrating another exemplary method ofpre-caching data in a system such as illustrated in FIG. 1.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENT

The following detailed description is directed to certain specificembodiments of the invention. However, the invention can be embodied ina multitude of different ways as defined herein. In this description,reference is made to the drawings wherein like parts are designated withlike numerals throughout.

FIG. 1 is a block diagram depicting one embodiment of an electronicdevice 100. The electronic device 100 may include personal computers,servers, mobile computers, mobile telephones, global positioning system(GPS) units, personal′ digital assistants (PDAs), or automobilenavigation system, or any other suitable type of electronic device. Inone embodiment, the electronic device 100 is configured for use by amobile user.

In one embodiment, the electronic device 100 is associated with aparticular user or a vehicle. The device includes a data processor ormicroprocessor 102, a memory or data storage 104, an output device 106,and one or more input devices 108. The microprocessor 102 may be anyconventional general purpose single- or multi-chip microprocessor suchas a Pentium® processor, Pentium II® processor, Pentium III® processor,Pentium IV® processor, Pentium® Pro processor, a 8051 processor, a MIPS®processor, a Power PC® processor, an ALPHA® processor, or any othersuitable processor. In addition, the microprocessor 102 may be anyconventional special purpose microprocessor such as a digital signalprocessor or programmable gate array.

Memory refers to electronic circuitry that allows information, typicallycomputer data, to be stored and retrieved. Memory can refer to externaldevices or removable storage systems, for example, disk drives, opticaldrives, tape drives, or non-volatile memory devices. Memory can alsorefer to fast semiconductor storage (chips), for example, Random AccessMemory (RAM) or various forms of Read Only Memory (ROM), that aredirectly connected to the processor or removably connected to theprocessor. Removably connected memory may include memory on anystandardized or proprietary device such as a memory card, a securedigital memory card, a memory stick, or any other suitable removablememory device. In one embodiment, the memory 104 is a hierarchicalmemory model that includes, for example. a secondary cache memory offaster memory. e.g., SRAM and a main memory. which may be a slowermemory, e.g., DRAM. In one embodiment, the memory 104 includes solidstate persistent memory such as FLASH memory or magneto resistance RAM(MRAM). In one embodiment, the memory 104 includes a disk drive, e.g., amagnetic. optical, or magneto-optical drive.

The output device 106 may include one or more video and audio outputdevices, such as a display screen, a printer, or a voice synthesizer.The display screen may be any visual display device such as a liquidcrystal display (LCD), a cathode ray tube (CRT). plasma, OLEO (OrganicLight Emitting Diode), or any other suitable display device. The outputdevice 106 may include devices such as loudspeakers for producingsounds. In one such embodiment, the audio output device 106 may includea vibrator device or other device configured to provide a relativelyinaudible signal to a user.

The input devices 108 may be a keyboard, rollerball, pen and stylus,mouse, multidirectional navigation button, or voice recognition system.The input device 108 may also be a touch screen associated with theoutput device 106. The user may respond to prompts on the display bytouching the screen. Textual or graphic information may be entered bythe user through the input device.

The electronic device 100 may communicate with other electronic devicesthrough one or more network interface devices. The network interfacedevices may include a first wireless transceiver 110. In embodiment, thefirst transceiver includes a relatively long range data communicationinterface such as a mobile telephone transceiver, a wireless datatransceiver, a satellite data transceiver, or another wireless networkinterface device. The electronic device 100 may also include a secondwireless transceiver 112. In one embodiment, the second transceiverincludes a shorter range communications interface including additionalradio interface protocols such as Bluetooth, IEEE 802.11, or otherwireless protocols. In one embodiment, the second wireless transceiver112 operates on an unlicensed spectrum band such as 2.5 GHz. In oneembodiment, the electronic device 100 also includes a wired datainterface 114, such as Ethernet, a serial port, a universal serial bus(USB) port, Firewire, IEEE1394, a synchronization cradle coupled to anetwork or other computing device, or an interface to a GPS receiver. Inone embodiment, the electronic device 100 includes an infraredcommunications link 116 or an optical frequency data link.

In one embodiment, the electronic device 100 includes a GPS receiver 120or other device configured to identify at least approximately thelocation of the device 100. In another embodiment, the electronic device100 is configured to communicate with an external GPS device 120 throughone of the network interface devices such as a serial port embodiment ofthe wired data interface 114 or through either or both of the wirelessdata transceivers 110 and 112.

It is to be recognized that embodiments may include only a portion ofthe components 104-120. For example, certain embodiments may onlyinclude a single wireless interface 110 or 112. Another exemplary device100 may include only a wired interface 114.

FIG. 2 is a block diagram depicting software modules of one embodimentof a system 200 for managing map data and geographically related data onan electronic device, such as the embodiment of a particular electronicdevice 100 a. The system 200 may include various modules 202-212. As canbe appreciated, each of the modules 202-212 comprises varioussub-routines, procedures, definitional statements, and macros. In oneembodiment, each of the modules 202210 is separately compiled and linkedinto a single executable program. In another embodiment, each of themodules may comprise separate executable programs on the electronicdevice 100. Thus, the following description of each of the modules202-212 is used for convenience to describe the functionality of variousembodiments of the invention. Thus, the processes that are undergone byeach of the modules 210-212 may be arbitrarily redistributed to one ofthe other modules, combined together in a single module, or madeavailable in a shareable dynamic link library. The functionality andexecution of the modules 202-212 may be managed by an operation system(not shown). Further, each of the modules 202212 could be implemented inhardware or located off the device on a server. In one embodiment, oneor more of the system modules 200-212 can be located on anetwork-connected device, such as an Internet server, a remote computer,or an external computing device. An external computing device may bedesktop, server, portable, hand-held, set-top, embedded, or any othersuitable computing device connected to the electronic device 100 by anetwork. In particular, the geocoding engine 208 can be located can on anetwork connected device or an external computing device, which reducesthe memory storage requirements for the electronic device 100.

In one embodiment, the system 200 includes a mapping application module202 that is configured to receive, store, transmit, and manipulatemapping data and geographically referenced content. The mappingapplication module may communicate with other electronic or computingdevices via a network interface module 204. In one embodiment, thenetwork interface module 204 uses one or more of the network interfacedevices 110, 112, 114, 116, to communicate with a network 220. Thenetwork may include any type of electronically connected group ofcomputers including, for instance, the following networks: Internet,Intranet, Local Area Networks (LAN), Wide Area Networks (WAN) orWireless Local Area Networks (WLAN). In addition, the connectivity tothe network may be, for example, remote modem, Ethernet (IEEE 802.3),Token Ring (IEEE 802.5), Fiber Distributed Datalink Interface (FDDI) orAsynchronous Transfer Mode (ATM). Note that computing devices may bedesktop, server, portable, hand-held, set-top, embedded or any otherdesired type of configuration. As used herein, the network includesnetwork variations such as the public Internet, a private network withinthe Internet, a secure network within the Internet, a private network, apublic network, a value-added network, an intranet, and the like.

The network may 220 may provide communication to one or more otherelectronic devices 230 that also include the map data and geographicallyreferenced content system 200. The geographical map data geographicallyrelated content may be transmitted by any suitable data protocol such asInternet Protocol (PI) including application level protocols such SMTP,SMS, 1M, or HTTP. The network 220 may also provide communication withone or more servers 240. In one embodiment, the server 240 is a webserver. In other embodiments, the server 240 may respond to any othersuitable client-server or peer-to peer protocol. In one embodiment, oneor more other electronic devices 100 b that include the system 200 arealso in communication with the network 220.

Embodiments of the system 200 may include a user interface module 206.In one embodiment, the user interface 206 includes a graphical userinterface. The user interface 206 may be output through the displaydevice 106. In one embodiment, the user interface 206 may produce soundsor activate a vibrator device.

The mapping application module 202 may be configured to interface with ageocoding engine module 208. The geocoding engine module 208 isconfigured to translate between address data, such as street addresses,and geographic coordinate information, such as latitude and longitude.In one embodiment, the geocoding engine module 208 is configured totranslate between different geographic coding systems. For example, inone embodiment, the geocoding engine module 208 is configured totranslate between latitude and longitude and another Cartesiancoordinate system. In one embodiment, geographically related contentincludes a geographic index that associates a range of geographiccoordinates with a portion of a map. In one embodiment, map data issegmented into data portions that are each associated with a particulargeographic index. In one embodiment, the map data may be segmenteddifferently at a number of zoom levels, e.g., in more blocks at moredetailed zoom levels and fewer blocks at higher zoom levels. Forexample, a metropolitan area may be represented by a single map segmentat the highest zoom (least detailed) level, in 32 blocks at the nexthighest zoom level, and in 256 blocks at the lowest (most detailed)level. In one such embodiment, geographically referenced content havinggeographic coordinates that fall within a particular segment of map dataare referenced by the geographic index of that map segment. In oneembodiment, geographically referenced content is referenced bygeographic indices that identify the map segment and a zoom level of themap segment. One embodiment of a geographic index is discussed in moredetail with reference to FIG. 14A. More details of one embodiment of amap coordinate conversion scheme are disclosed in the above incorporatedU.S. Pat. No. 6,703,947.

In one embodiment, the mapping application module 202 is configured tocommunicate with an application programming interface (API) module 210.The API module 210 is configured to interface the mapping applicationmodule 202 with other applications or data sources 211 such as an emailprogram, an Internet browser, a web server, a contact manager, or anyother software application or information stored, received, or input tothe device 100.

In one embodiment, the mapping application module 202 is also configuredto communicate with a database module 212. The database module isconfigured to store, search, and retrieve stored data. In oneembodiment, the data is stored in the memory 104. In another embodiment,the database module 212 accesses the data by communicating with a remotedatabase over the network 220.

In one embodiment, the mapping application module 202 is configured tocommunicate with one or more map and geographic based content servers todownload map data and geographic based content as needed. In oneembodiment, the mapping application module 202 maintains a local cacheor store of map data. This data may be stored by the database module212. More details of one embodiment of a map caching scheme aredisclosed in U.S. Pat. No. 6,703,947, which is hereby incorporated byreference.

FIG. 3 is a schema diagram illustrating data formats of one embodimentof the system 200. Data in the schema may be stored in a structureddatabase of records, text files, binary data files or other suitablefile format. In one embodiment, each schema element is associated withone or more tables in a relational database. More details of the schemaelements are described below with reference to embodiments of variousmethods. In one embodiment, geographically referenced content includesone or more pushpins. Generally, geographically related content such asa pushpin describes a location or object such as an asset, a person, avehicle, an organization such as a business, a charity, an educationinstitution, governmental entity that is referenced to geographicaldata. In one embodiment, as illustrated in FIG. 3, a pushpin dataelement includes geographic location indicators such as latitude andlongitude, pseudo-coordinates or geographic location indexes along withfields identifying the pushpin, e.g., a name, street or postal addressand other information about the person or object related to the pushpinlocation. In one embodiment, pushpin data may include other contact datasuch as hours of operation, personal information about a contact orinformation about vehicles of the contact.

Various other data items may be associated with pushpins. For example, adisplayable layer may be associated with a pushpin. In one embodiment,the mapping application module 202 can be configured to selectivelydisplay pushpins that are associated with one or more layers. An iconimage for displaying the geographically related content such as apushpin on a map may also be associated with each pushpin. In oneembodiment, the mapping application module 202 can be configured toselectively display′ only those pushpins associated with one or moreicons images or data identifying an icon, e.g., an icon index. In oneembodiment, the mapping application module 202 can be configured toselectively display only those push pins associated with one or moreicons images identifiers.

In one embodiment, the mapping application module 202 can be configuredto selectively display only those pushpins associated with theparticular data values contained in one or more of the data fieldsassociated with a pushpin, such as pushpin name, pushpin comments,pushpin data value, pushpin attribute, address, zip code, municipality,country, location index number, map segment index, coordinate range,phone number, Internet address, email address, user identifier, deviceidentifier, etc.

Embodiments include methods of sending pushpins between one or moreelectronic devices 100. For example, these methods include sending amessage or instruction to a device 100 that includes the system 200.This message or instruction starts the system 200 (if it is not alreadyrunning in the background) and then displays custom pushpin(s) at theposition(s) requested and fills in all the associated the pushpin datafields. The originating device 100 a sends a message containing theinformation about the pushpin(s) and the identity of the destinationdevice to the web server 240. The web server then sends a short messagesystem (SMS) or other message or communication to the device telling itthat there is a pushpin (or set of pushpins) to be received from the webserver 240 and gives the destination device an access code (perhapsconsisting of the web server address, user account and a password). Thedestination device 100 b then accesses the web server with the useraccount and access code and downloads the information regarding thepushpin(s).

One embodiment is a method of sending multiple pushpins from an Internetbrowser so that a user with access to the Internet can send one or morepushpins and associated data to any suitable destination device 100 b.In one such embodiment, the Internet browser sends the pushpininformation and information identifying the destination device to theintermediate web server 240. In one embodiment, the web server 200 thensends a message to the device notifying the destination device thatthere is a pushpin (or set of pushpins) to be received from the webserver 240. In one embodiment, the notification is an SMS message.

It is to be recognized that in other embodiments, the notificationmessage may be sent using any suitable communication protocol, includingthose discussed herein. The notification message may also include anaccess code. In one exemplary embodiment, the access code includes theweb server address, a user account and a password. The destinationdevice 100 b then accesses the web server with access code and downloadsthe information regarding the pushpin(s). In one embodiment, software orhardware on the destination device starts the system 200 if it was notalready running. The system 200 can then display the positions of thereceived push pins.

One embodiment is a method of sending multiple push pins via anintermediate website to other devices. This enables individual users tosend their location to a central location register and retrieve thelocations of other pushpins within a certain geographic region or with aspecific set of search criterion. For example, individual devices 100may send their pushpin locations and associated information to theintermediate website. Dependent on the location of the device, theintermediate server may send back to the device a set of pushpins withina predetermined geographic area, which meet the desired criteria. As thedevices 100 move around, they may update their location, for example,with a frequency based upon the distance moved, including data such asthe current map segment index number, the time between location updates,etc.

Other embodiments include methods' of sending multiple location pushpinsvia a peer-to-peer architecture. Individual users may send their,locations directly to other users and retrieve the locations of yetother pushpins within a certain geographic region, without going througha central server. In one embodiment, users can ask for the location ofanother specific user and get that information from other users in thenetwork that happen to know where that user is currently. Thus, suchembodiments do not include a central database or intermediate server.

FIG. 4 is a flowchart illustrating one embodiment of a method ofcommunicating a pushpin between applications on the electronic device100. Beginning at block 410, a pushpin or other geographic based dataassociated with one or more pushpins is entered or activated on theelectronic device 100. Next at block 420, the system 200 captures thelocation or pushpin information via the API module 210. In oneembodiment, another software application on the electronic device 100sends a message to the system 200 to display the pushpins. In oneembodiment, the pushpin message is sent, e.g., as a startup parameter orinstruction, to the system 200. In another embodiment, API moduleinterfaces with an interprocess communication (IPC) mechanism such asthose provided by operating systems to receive the pushpin message. Nextat decision block 430, whether the mapping application module 202 isexecuting or initialized is detected. If the mapping application moduleis not executing, it is started at block 440. Next at block 450, thepushpin data, which may include one or more pushpins, is imported intoan appropriate displayable layer by the mapping application module 202.The pushpin data may associate a layer identifier associated with theeach pushpin. In one embodiment, if no layer identifier is associatedwith each pushpin, a layer may be selected based on a comparison ofpredetermined criteria with the existing pushpin data on the device, orbased on a set of pre-determined rules about how to associate pushpindata with layer identifiers.

Moving to decision block 460, the pushpin data is checked for coordinatedata. If no data is found, the method proceeds to block 470. At block470, the mapping application module 202 associates coordinateinformation with the pushpin using the geocoding engine module 206,which may be located in the system 200, on the device 100, or on aremote web server 240. Next at block 480, the pushpin data is importedinto the appropriate displayable layers in the database module 212.Proceeding to block 490, the pushpins are displayed using the userinterface module 204, e.g., to the display 106.

Another embodiment includes a method of communicating data from themapping application 202 to another application or data source 211 suchas an address or contact manager. In one embodiment, a user selects apushpin, multiple pushpins, or a layer of pushpins and invokes a userinterface, such as a menu button. In one embodiment, the mappingapplication module 202 sends the pushpin data to another application ordata source 211, via the API module 210. In one embodiment, the userinterface module 206 provides a control such as a menu item thatprovides the user with an option to send one or more pushpins and theirassociated data in a selected map layer to another application or datasource 211.

FIG. 5 is a flowchart illustrating one embodiment of a method ofcommunicating pushpin data directly between electronic devices 100.Beginning at block 510, pushpin data is entered on a source electronicdevice 100. Next at block 520, the source device communicates thatpushpin data to a destination electronic device 100 via the network 220.The pushpin data may be communicated using any type of electroniccommunication, including Email.SMS/IM.InternetMessage.an HTTP Command orany other suitable electronic message. Moving to block 530, the pushpindata is received by the system 200 on the destination device 100 b. Nextat block 540, the system 200 either automatically, or after prompting auser, sends the data to the mapping application. The method thenproceeds to block 430 of FIG. 4 and the method continues as describedabove with reference to FIG. 4.

FIGS. 6A-6C are display screen images from the source device 100illustrating exemplary views associated with entering pushpin data andsending the pushpin data to a destination device as described above withreference to blocks 510 and 520 of FIG. 5. FIG. 6D is a display screenimage from the destination device 100 b illustrating exemplary viewsassociated with blocks 530 and 540 of receiving the pushpin data on thedestination device.

FIG. 7 is a flowchart illustrating one embodiment of a method ofcommunicating pushpin data from an originating device to an intermediateserver. In one embodiment, the originating device includes an Internetbrowser. In one embodiment, the intermediate server may include a webserver. In other embodiments, the intermediate server may be any otherelectronic device 100 that includes the system 200, or modules of thesystem 200. Beginning at block 710, pushpin data is entered on anoriginating electronic device 100 a or on an Internet browser. Next atblock 720, the originating device or Internet browser communicates thatpushpin data to the intermediate server via the network 220. Thepushpin′ data may be communicated using any suitable type of electroniccommunication, including Email, SMS/IM, Internet Message, or an HTIPCommand. Moving to block 730, the pushpin data is received by theintermediate server. Next at decision block 740, the intermediate serverdetermines whether the originating device 100 a or Internet browser isauthorized to send data to the intended destination device 100 b. If theoriginating device is not authorized to send the message to thedestination device, the method proceeds to block 750. At block 750, theintermediate server sends a reject message back to the originatingdevice 100 a or originating Internet browser and stops processing themessage containing the pushpin data. If the originating device isauthorized, the method proceeds to block 760 in which the pushpin datais stored on the intermediate server. In one embodiment, the pushpindata is checked for the presence of geographic coordinate data and thenintegrated into the appropriate geographic related content databaselayer by the mapping application module 202 on the intermediate serveras described in blocks 460-480 of FIG. 4. If the pushpin data receivedon the intermediate server does not include the coordinates, then thegeocoding engine module 208 in system 200 determines the coordinates andadds them to the respective pushpin data.

FIG. 8 is a flowchart illustrating one embodiment of a method ofcommunicating pushpin data between electronic devices 100 via theintermediate server. Beginning at block 810, pushpin data is entered onan originating electronic device 100 or an Internet browser. Next atblock 820, the originating device or Internet browser communicates thatpushpin data to the intermediate server via the network 220 indicatingthat the data is destined for a second electronic device 100. Thepushpin data may be communicated using any suitable type of electroniccommunication, including Email, SMS/IM, Internet Message, or an HTTPCommand. Moving to block 830, the pushpin data is sent to theintermediate server as described above with reference to FIG. 7. In oneembodiment, the pushpin data is stored in a file on the intermediateserver. In another embodiment, the pushpin data is stored in a database.

Next at block 840, the intermediate server sends the pushpin file accessdata or pushpin database access data to the destination device 100 b.Moving to block 850, the system 200 receives the intermediate serveraccess data on the destination device 100 b. Next at block 860, thesystem 200 either automatically, or after prompting a user, sends theintermediate server access data to the mapping application module 202.Next at decision block 865, whether the mapping application module 202is executing or initialized is detected. If the mapping applicationmodule is not executing, it is started at block 870. Next at block 870,the mapping application uses the intermediate server access data toauthorize retrieval of the pushpin data from the intermediate server.Moving to block 880, the pushpin data is imported into the appropriatecustom layers in the mapping application module 202 and stored indatabase module 212. Proceeding to block 890, the pushpins are displayedusing the user interface module 204, e.g., to the display 106.

Other embodiments include methods of an originating device to requestpushpins from another destination device 100 b or an Internet server. Incertain embodiments, these methods include the originating devicesending a message or instruction to the system 200 on the destinationdevice 100 b to request that the destination device running the system200 transmit a response message or instruction back to anotherpredetermined location, Internet server or device 100. The responsemessage or instruction from the destination device may containinformation for custom pushpins at some location of interest, e.g. thecurrent device location, the future device position, past deviceposition, position of other devices, points of interest, pushpinlocations, text message, etc.

The requested pushpin data may be from a number of sources: anotherapplication running on the destination device 100 b (such as an email orSMS client, address book, calendar, contact manager, database program,enterprise application, inventory control, dispatch, asset tracking,parcel shipping, fleet management, etc.), another device 100 running thesystem 200, another device running another application (such as an emailor SMS client, address book, calendar, contact manager, databaseprogram, enterprise application, inventory control, dispatch, assettracking, parcel shipping, fleet management, etc.), direct input to thedevice from a command console (e.g. via serial port, USB port, etc.), anInternet browser connecting to a website, a central (location register)website, e.g., as used in ICQ, IM applications, etc., an Internetserver, e.g. an FTP server, a map data server, an address lookup server,etc.

As with pushpin data sent by embodiments of the methods described above,the message data sent either from the intermediate server to thedestination device 100 b or from the originating device 100 a mayinclude an Internet command message (e.g. HTTP, ICQ, proprietaryInternet message format, etc.), a text file stored on a webpage, a textfile stored on an FTP server, an email, an SMS message, or communicationdirectly with the system 200 running on the device, after a remoteconnection has been established. Pushpin data may include pushpinname(s), e.g. single or multiple pushpin(s), start pushpin, finishpushpin, intermediate stop (waypoint) pushpins, etc., pushpin comments,pushpin icons, pushpin addresses, pushpin appointment times, pushpinlocation (e.g. coordinates, pseudo-coordinates, etc.), pushpin locationindex number, pushpin phone number, pushpin Internet address, pushpinemail address, pushpin layer, inter-pushpin driving directions text androute segment coordinates or pseudo-coordinates, source device 10 (e.g.IP address, SMS number, email address, phone number, pseudonumber/identifier, device 10, user name, vehicle identifier, locationidentifier, personal identifier, etc.), destination device 10 (e.g. IPaddress, SMS number, email. address, phone number, pseudonumber/identifier, device 10, user name, personal identifier, etc.), orsource device message type/format.

FIG. 9 is a flowchart illustrating one embodiment of a method 900 ofrequesting pushpin data from another electronic device 100. The method900 begins at a block 910 in which a message is sent from theoriginating device to the destination device requesting pushpin data.The message may be sent using a protocol such as email, SMS/IM, or anInternet message. Next at block 915, the system 200 on the destinationdevice 100 b receives the request. Moving to block 920, the system 200either automatically, or after prompting a user, sends the pushpin datarequest to the mapping application module 202. Next at decision block925, whether the mapping application module 202 is executing orinitialized is detected. If the mapping application module is notexecuting, it is started at block 930.

Proceeding to decision block 935, the mapping application module 935determines whether the originating device is authorized to request thepushpin data from the destination device. In one embodiment, theauthorization is based on comparing the originating device with a listof devices. In another embodiment, a suitable cryptographic key exchangeprotocol may be used to determine whether the originating device 100 ais authorized. If not, at block 940, a message rejecting the request isreturned to the originating device 100 a and the method ends. If theoriginating device 100 a is authorized to make a request, the pushpindata is sent in a message from the destination, device 100 b back to theoriginating device 100 a. Moving to block 950, the message is receivedby the system 200 of the originating device 100 a. Next at block 955,the system 200 either automatically, or after prompting a user, sendsthe pushpin data to the mapping application. The method then proceeds toblock 430 of FIG. 4 and the method continues as described above withreference to FIG. 4.

FIG. 10 is a flowchart illustrating one embodiment of a method ofrequesting a pushpin from an intermediate server. The method begins at ablock 1010 in which a message is sent from the originating device 100 ato the intermediate server requesting pushpin information. The pushpinrequest message may be sent using any protocol such as email, SMS/IM, oran Internet based message. Next at block 1020, the system 200 on theintermediate server receives' the request. Proceeding to block 1030, theintermediate server determines whether the originating device, 100 a isauthorized to request the pushpin data. In one embodiment, theauthorization is based on comparing the originating device with a listof authorized devices. In another embodiment, a suitable cryptographickey exchange protocol may be used to determine whether the originatingdevice 100 a is authorized to make a request. If not, at block 1040, amessage rejecting the request is returned to the originating device 100a and the method ends. Next at block 1050, if the originating device 100a is authorized, the pushpin data is sent in a message from theintermediate server back to the originating device 100 a. Moving toblock 1060, the message is received by the system 200 of the originatingdevice 100 a. Next at block 1070, the system 200 either automatically,or after prompting a user, sends the data to the mapping application.The method then proceeds to block 430 of FIG. 4 and the method continuesas described above with reference to FIG. 4.

FIG. 11 is a flowchart illustrating an exemplary method 1100 ofrequesting pushpin data from another electronic device 100 via anintermediate server. The method 1100 is similar to the method 900illustrated by FIG. 9 except that an intermediate server receives therequest for the pushpin data from the originating device 100 a andforwards that request to the destination device 100 b and then theintermediate server returns any resulting pushpin data from thedestination device back to the originating device 100 a.

The method 1100 begins at a block 1110 in which the system 200 sends acommunication such as an email, SMS/IM, instant or Internet message fromthe originating device 100 a to the intermediate server 240 to requestpushpin information. Next at a block 1112, the intermediate server 240receives the communication. Moving to block 1114, the intermediateserver 240 determines whether the originating device 100 a is authorizedto request the pushpin from a particular destination device 100 b. Ifthe device is not authorized, the method 1100 proceeds to a block 1116in which the intermediate server 240 sends a communication back to theorigination device 100 a rejecting the request. The method 1100 thenterminates. If the device is authorized, the method 1100 proceeds to ablock 1120 in which the intermediate server 240 sends a communicationincluding the request to the destination device 100 b for the pushpininformation.

Next at a block 1122, the destination device 100 b receives thecommunication containing the request. Proceeding to a block 1124, thedestination device 100 b sends instructions to the mapping applicationthat includes the pushpin request information. In one embodiment, thesystem 200 on the device 100 b prompts the user to manually instruct themapping application module 202 to process the request. In anotherembodiment, the system 200 automatically instructs' the mappingapplication module 202 to process the request. In one embodiment, thesystem 200 executes the mapping application if needed.

Proceeding to block 1132, the mapping application module 202 determineswhether the intermediate server 1132 is authorized to request pushpindata from the destination device 100 b. In one embodiment, thedetermination is based on a list of authorized servers 240. In anotherembodiment, the determination is based on a comparison of request datawith predetermined criteria established by the user such as theoriginating device 100 a, a user of the originating device 100 a, or onportions of the requested pushpin data. If the requestor is notauthorized, the method 1100 proceeds to a block 1134 in which thedestination device 100 b sends a communication back to the intermediateserver rejecting the request. If the requestor is authorized, the method1100 proceeds to a block 1136 in which the mapping application module202 retrieves the requested pushpin information.

Moving to a block 1140, the system 200 communicates the requestedinformation to the intermediate server 240. Next at a block 1142, theintermediate server 240 communicates the requested pushpin informationto the originating device 100 a.

Proceeding to a block 1144, the system 200 of the originating device 100receives the pushpin and either automatically or manually (e.g., byprompting a user via a user interface) provides the information to themapping application module 202. In one embodiment, the system 200executes the mapping application if needed. Next at a block 1152, themapping application module 202, receives the pushpin data and displaysit at the appropriate location on a map.

Embodiments also include methods for performing pushpin commands. FIG.12 is a flow diagram illustrating a set of exemplary commands. Themethod begins at block 1210, where the system 200 receives an input, forexample, tapping on a custom pushpin to activate a menu. Next at block1220, the system 200 receives a command selection from the menu.Commands may include sending pushpin data and associated information toanother device 100 or remote location, dialing a predetermined phonenumber, starting an Internet browser at a predetermined URL, sending anemail to a predetermined location, sending an SMS message to apredetermined address, adding a contact to the address book of thedevice 100, adding an appointment to the calendar of the device 100,starting another application on the device 100 and send it a command orinstruction, or downloading to the device 100 a further map, floor plan,or other content relating to that pushpin, for example.

Another embodiment includes a method of intelligently caching mapsegments. The method includes intelligently downloading and storing mapsegments on the, electronic device 100 to ensure that newly requestedmap segments get downloaded and cached and previously downloaded andcached map segments get retrieved and instantly displayed. In addition,map segments which have not been viewed recently get discarded from themap cache first, map segments which are rarely viewed get discardedfirst, and segments with low_significance (based on last view date andtime and number of views) and lowest zoom level get deleted first, suchthat the memory available to the device does not tend to getover-filled. Thus, as many map segments are stored as possible on thedevice and the most relevant map segments are deleted last from the mapsegment cache. Further, map processing time or processor power can bereduced because only the map segments which are currently beingdownloaded or retrieved from cache need to have the counters indicatingtheir respective map segment relevancy updated.

FIG. 13 is a flowchart further illustrating such an exemplary method1300 for managing a cache of map data. The method 1300 begins at a block1310 when the mapping application module 202 is installed on the device100 and a counter (e.g., labeled “Time Period Since Install”) iscreated. Next at a block 1315, the counter is updated with the currentnumber of days, or other measure of the time period since installationof the system, whenever the system 200 is started up. Moving to a block1320, the system 200 is used to view one or more map segments.

At a decision block 1325, the cache is checked for the desired mapsegments, for each segment not in the cache, the method 1300 proceeds toa block 1335 in which the map segments are downloaded. Next at a block1340, each downloaded map segment is assigned a number of “ActivityPoints”. In one embodiment, this value is set to be the current “TimePeriod Since Install” plus some “Download Credit,” for example, 365. Ifa map segment was retrieved from cache at the block 1325, then themethod 1300 proceeds to block 1330 in which the number of “ActivityPoints’ assigned to that segment is updated to the current “Time PeriodSince Install” plus some “Cache Retrieval Credit”, for example, 180.Next at bock 1345, the system 200 updates a ranked table containing themap segment identifier and the corresponding number of ‘ActivityPoints’, sorted by number of “Activity Points”’. The table may also besorted by zoom level of the map segments.

Next at a decision block 1350, the system 200 determines whether the“Cached Segment Memory” exceeds a predefined threshold value (“MaximumAllowable Cached Segment Memory”) or if overall device memory fallsbelow a threshold. If the thresholds are not exceeded the method 1300terminates. If the thresholds are exceeded, the method 1300 proceeds toa block 1360 in which the map segments with the lowest number of“Activity Points” gets deleted first, until the “Current Cached SegmentMemory” is reduced to a predefined “Nominal Cached Segment Memory”threshold. If multiple segments have the same lowest number of “ActivityPoints”, the system 200 deletes the segments with the lowest zoom levelfirst, i.e., those segments that cover the smallest geographic area. Ifmultiple segments have the same “Activity Points” and the same lowestzoom level then the system 200 deletes the segments with the lowesttotal (of the 8) adjacent segment “Activity Points”. If multiplesegments still have equal lowest number of “Activity Points”, then themap segments may be deleted one by one in order, until the “CurrentCached Segment Memory” is reduced to the predefined acceptable (“NominalCached Segment Memory). The method 1300 then terminates.

Another embodiment includes a method of pushpin indexing. The methodincludes associating each pushpin with a geographic index number or aseries of index numbers or identifiers. In one embodiment, these indexnumbers are used to display only pushpins within the currently retrievedmap segments or currently displayed map area or some other predefinedgeographic region. In one embodiment, the index numbers are used toselect pushpins within the currently retrieved map segments or currentlydisplayed map area or some other predefined geographic region for queryor download. In another embodiment, pushpins are selected based on beingassociated with the predetermined identifier. The use of the indexnumber in such embodiments tends to speed the selection and processingof the desired pushpin data and hence speeds the display of the pushpinsof interest. In some embodiments, as the map area is updated in cache,the index numbers are used to automatically download, cache, or deletethe pushpins for the corresponding map segments in the custom layerswhich are loaded in cache. The use of geographically based index numbersenormously speeds processing and display when viewing layers with verylarge numbers of pushpins, e.g. nationwide store locations, real-estatedatabases, yellow pages, etc.

In one embodiment, the pushpin indexes are calculated according to theequations in Table 1. In the equations below, the values prefixed withTMB, TMC, and TMD refer to indexes at three particular zoom levels inorder from highest to lowest zoom level. The equations prefixed by TVare used to convert from Latitude/Longitude coordinates into a positiveinteger based coordinate scheme. More details of one embodiment of a mapcoordinate conversion scheme are disclosed in the above incorporatedU.S. Pat. No. 6,703,947.

TABLE 1   TV_Lat_Coords = ROUND ((180 − 2 * Latitude)) * 64 * 16000),${Latitude} = \left( {90 - \left( \frac{{TV\_ Lat}{\_ Coords}}{2*64*16000} \right)} \right)$TMB_Lat = 180 − (2 * CEILING (Latitude, 1/2)),   TMC_Lat = 8 * ( (180 −(2 * CEILING (Latitude, 1/16))),   TMD_Lat = 64 * (180 − (2 * CEILING(Latitude, 1/128)))   TV_Lon_Coords = ROUND ((360 + Longitude) * 64 *32000),   ${Longitude} = \left( {90 - \left( \frac{{TV\_ Lon}{\_ Coords}}{64*32000} \right) - 360} \right)$  TMB_Lon = 360 + CEILING (Longitude, −1),   TMC_Lon = 8 * (360 +CEILING (Longitude, −1/8)),   TMD_Lon = 64 * (360 + CEILING (Longitude,−1/64))

FIG. 14A is a flowchart illustrating one embodiment of a method ofdetermining index numbers. Beginning at a block 1410,geographically-based pushpin data is downloaded. Next at block 1420, thepushpin data may be optionally converted from a standardLatitude/Longitude coordinate scheme to the map application's coordinatescheme, such as by using the equations in Table 1 for converting betweenlatitude and longitude and TV_LonCoords and TV_Lat_Coords. Moving toblock 1430, the system 200 assigns geographical index values to eachpushpin in the map data based on equations such as in Table 1 forcalculating indexes in the zoom levels associated with the identifiersTMB, TMC, and TMD.

FIG. 14B is a flowchart illustrating one embodiment of a method ofdisplaying pushpins based on the pushpin index. Beginning at block 1450,map layers are selected for display. Next at block 1455, the maplocation and associated map segments are downloaded or retrieved fromcache. Moving to block 1460, the pushpins in selected layers are queriedand pushpins from the result set are individually processed in blocks1465-1475. Next at decision block 1465, the geographical indexes of eachpushpin are compared to the current map segment identifier. If one ofthe pushpin indexes corresponds to the current map segment identifier,the method proceeds to block 1470, in which the pushpin is displayed. Ifnot, the method moves to block 1475 and the pushpin is not displayed.The method proceeds to block 1480, where the next pushpin is selectedfor display processing. In an alternative embodiment, rather than beingdisplayed or not displayed in blocks 1470 and 1475, the pushpins aremarked for display or non-display, or associated with a list or otherdata structure of displayed or non-displayed pushpins. In oneembodiment, the marked pushpins can then be saved to another geographiccontent layer, sent to an intermediate server 240 or sent to anotherdevice 100.

FIG. 15 is a flowchart illustrating one embodiment of a method 1500 ofdownloading pushpin data based on the pushpin zoom level index. In oneembodiment, each pushpin is identified with one or more zoom levels byrespective indices. In one embodiment, each pushpin is associated with arange of zoom level indices, a lowest level that corresponds to thegreatest zoom-in to the map, and a highest level zoom index thatcorresponds the greatest zoom-out of the map. In one embodiment, aparticular pushpin is only downloaded for display if the zoom level ofthe map corresponds to the zoom level range of the pushpin. The method1500 begins at block 1510 in which the user or another applicationselects the content layers to display on the map. Next at block 1520,the corresponding map location is selected and the corresponding mapsegments are downloaded from a map server or retrieved from the mapcache or database on the electronic device 100. Next at block 1530,currently displayed map segments and the segment indexes for the lowestlevel (e.g., highest zoom-in level) maps are identified. Moving to block1540, the system 200 cycles through all the pushpin lowest level indicesand content layers corresponding to the currently displayed mapsegments. Next at decision block 1550, each pushpin in cache is examinedin the currently selected content layers to determine whether thepushpin has the same lowest zoom level index as any of the currentlydisplayed map segments and their corresponding lowest zoom level mapsegment indexes. If not, the method proceeds to block 1560 in which thelowest level index and layer name is collected into a list of desiredpushpins sorted by lowest level index number and layer name. Next atblock 1570, a request is sent to an intermediate 240 server or anotherdevice 100 to provide the push pins in the list of desired pushpins byindex/layer. Moving to block 1580, the requested pushpins are downloadedfrom the intermediate server into custom content layers in the cache ofthe device 100. In one embodiment, the “empty” indexes for each layer onthe intermediate server, (Le., those indexes where no pushpins for thatlayer exist) are noted with a single pushpin with a blank icon and theappropriate indexes to act ˜s a data sentinel so that the system 200does not continuously attempt to download pushpin data from theintermediate server for layers and segment indexes which do not containany pushpins.

Another embodiment includes a method of multiple map segment downloadand deletion to enable the user to download multiple map segments,inspect what map segments are in cache and to delete one or more of themap segments. The user can thus simply inspect what segments are storedin cache and delete them if required, or if necessary do a large areamap pre-installation/download. For example, a user of a device 100 mayupdate the maps installed while it is in a network-connected environmentsuch as in its synchronization cradle or otherwise connected to anetwork so that the device 100 has maps available for an intended tripin which the device 100 may not always be connected to a network orotherwise have access to a map segment server 230. FIG. 16 is a screenshot illustrating exemplary views associated with one embodiment inwhich cached segments 1610 are presented in a different color or shadingfrom non-cached segments 1620. FIG. 17 a is a flowchart illustrating oneembodiment of method of indicating the cache status of map segment data.Beginning at block 1710, the user selects the map of, for example, the,US/Canada (or another smaller geographic area). Next at block 1712, agrid is displayed on the map, corresponding to the geographic boundaryof each of the segments at the different zoom levels, e.g. TMB (32 km),TMC (4 km), or TMD (500 m) as disclosed in the above incorporated U.S.Pat. No. 6,703,947. Moving to block 1714, all the map segments withinthe screen display area are queried to identify which map segments arestored in cache. Next at block 1716, if TMB, TMC or TMD segments areidentified as being stored in cache, then various different colors andshading are displayed in the respective grid regions to represent thepresence of the respective map segments in the map screen display areaat the different zoom levels. Alternatively, the user interface mayprovide the user with a control to toggle between the different grid andsegment sizes (i.e. the different map zoom levels), to display which mapsegments are stored in cache. Thus, the user may identify the segmentsin cache at any particular zoom level, by looking at the shaded sizesand colors or just by toggling between the various grid and segmenttypes (i.e., map segment zoom levels).

FIG. 17B is a flowchart illustrating another embodiment of a method ofmaintaining a cache of map data segments similar to the embodimentdepicted in FIG. 17A. Beginning at block 1720, the map grid is displayedas discussed in connection with FIG. 1710. Next at block 1722, afterviewing the map, if the user desires to download a large map area fromthe server, the user can select the segments to download by tapping onor otherwise selecting the respective segment grid. Next at blocks‘1724, the mapping application module 20′2 identifies the map segmentsindex numbers (from one or more of the different zoom levels) which arenot already stored in cache and requests such segments from the server.In one embodiment, the request to the map server may desirably beperformed by a single map data request, rather than asking for theindividual map segment data, one segment at a time. Moving to block1726, the map server sends the requested map segment data to the mappingapplication module 202, either one segment at a time or as a collectionof map segment data. Next at block 1728, the map segment cache 212 isupdated to include the additional data.

FIG. 17C is a flowchart illustrating a method of providing a userinterface for a user manually maintain a cache of map data. Beginning atblock 1730, a grid showing map segments is presented as discussed inconnection with FIG. 17 A. Next at block 1732, the user taps on thescreen display interface module 206 to select map segments to bedeleted. Moving to block 1734, the mapping application module 202deletes the selected map segments from memory or the store of thedatabase module 212. Proceeding to block 1736, the map segment databaseis updated to reflect the current map cache.

Another embodiment includes a method of storing a particularpresentation of a map in a list of favorites. Simply storing aparticular map location does not allow a user to conveniently view a mapusing previously identified desirable settings. A handheld device may beused while walking or driving and may have more limited controls than adesktop computer or similar computing device. Thus, it has been foundthat it is desirable to provide a user with a simple interface forstoring some particular presentations of a map and geographic basedcontent for later viewing. The elements of the presentation that may besaved include the current screen settings, i.e. map center location,zoom level, custom layers, etc. In one embodiment, the user interfacemodule 206 provides an interface for the user to save the current screensettings, i.e. map center location, zoom level, custom layers, etc. byjust selecting “Add Favorite” and then the current settings are saved towhatever name is preferred. For example, a ‘Favorite’ might be named“San Diego Museums,” “Toronto Libraries,” etc. FIGS. 18A-D areflowcharts that illustrate embodiments of methods of manipulatingfavorites. FIG. 18A. is a flowchart depicting one embodiment of a method1800 of creating a favorite via, e.g., user interface module 206. Themethod 1800 begins at a block 1802 in which a user selects the desiredsettings data. This data may include one or more of a map centerlocation, a map screen zoom level, a list of visible custom contentlayers, specific pushpin, or other suitable data. Moving to a block1804, the user selects a name (or enters a new name) of a favorite. Theuser interface module 206 receives the selected settings and storesthese settings in association with the favorite.

FIG. 18B is a flowchart depicting one embodiment of a method 1810 ofselecting and displaying a previously created favorite. The method 1810begins at a block 1812 in which the user selects a desired “favorite” ina user interface. In one embodiment, the user interface module 206provides a pull down list of favorites from which the user may select.In other embodiments, the user interface module 206 may provide anyother suitable user interface component for allowing the user to selector enter a favorite. Next at a block 1814 the user interface module 206loads the selected settings data and provides displayed dataaccordingly. These settings may include one or more of a map centerlocation, a map screen zoom level, a list of visible custom contentlayers, specific pushpin, or other suitable data.

FIG. 18C is a flowchart depicting one embodiment of a method 1820 ofupdating the map and presentation associated with a previously createdfavorite. The method 1820 begins at a block 1822 in which a user selectsthe desired settings data. This data may include one or more of a mapcenter location, a map screen zoom level, a list of visible customcontent layers, specific pushpin, or other suitable data. Moving to ablock 1804, the user selects a name (or enters a new name) of afavorite. The user interface module 206 receives the selected settingsand stores and updates these settings in association with the favorite.

FIG. 18D is a flowchart depicting one embodiment of a method 1830 ofdeleting a favorite. The method 1830 begins at a block 1832 in which theuser selects a desired “favorite” in a user interface. In oneembodiment, the user interface module 206 provides a pull down list offavorites from which the user may select. In other embodiments, the userinterface module 206 may provide any other suitable user interfacecomponent for allowing the user to select or enter a favorite. Next at ablock 1834 the user interface module 206 deletes settings dataassociated with the selected favorite.

Another embodiment includes a method of displaying a list of preferredlocations, such as cities and airports for regions, states, orprovinces. In one embodiment, the user interface 206 provides a pulldown list of cities and airports that can be found quickly, e.g., a“QuickFind” list. In one embodiment, rather than simply display the listof locations in a particular region or state using a sorting rule, suchas alphabetically, the list of locations in a particular region, state,or province may be ordered based on the preferred locations, such as thelargest city and main airport that are within that selected region,state or province. Thus, the preferred locations are provided to theuser for easier and quicker access to those preferred locations, whichare most likely to be selected by the user. In one embodiment, the usersquickly select the most likely locations they want to find by selectingthe “QuickFind” feature and the desired region, state or province andthen the most likely selected (Le. popular) locations are listed firstin the pull-down list.

FIG. 19A is a flowchart illustrating one embodiment of a method forcreating a list of preferred locations. Beginning at block 1910, a listof cities, airports, or other geographic points of interest is createdin alphabetical (or another sort order) for each state, province, orgeographic region. Next at block 1920, a preferred location flag is setfor one of the items in the list of preferred locations. For example,FIG. 19B is a screen shot illustrating exemplary views associated with agraphical user interface for selecting a particular region, e.g., theState of California, with Los Angeles selected as the preferred city.FIG. 19C is a screen shot illustrating exemplary views associated with auser interface for selecting a preferred airport in that region, e.g.,LAX (Le. Los Angeles Airport). Moving to block 1930, when a “QuickFind”menu for a state, province, or region is presented, the selectedpreferred locations are displayed at the top of the list. In anotherembodiment, the selected preferred locations are displayed as thedefault selection of a menu or other suitable user interface control.

Another embodiment includes a method to display municipality names basedon the number of cities and towns and other municipalities within thescreen display area. In metropolitan areas, the number of municipalitieswithin the screen area is very high and the screen tends to becomecluttered if too many location names are displayed. In rural areas, thenumber of municipalities is typically lower. In an embodiment in whichonly cities or towns of a predetermined size or population aredisplayed, small towns may not be displayed, except at the highestzoom-in levels. It is more desirable when displaying rural areas, todisplay even the smallest towns. For example, when driving across adesert with no large towns, the display of even the smallest hamlet ishelpful for a user to determine position, estimate time of arrival,confirm being on-route, etc.

FIG. 20A is flowchart illustrating one embodiment of a method ofencoding data to facilitate the display of location names based on thenumber of locations within the display area. Beginning at a block 2010,locations, e.g., municipalities such as cities, towns or villages, areassigned map segment locations based on the coordinates of eachlocation. Next at block 2020, the locations are sorted into differentbins based on municipality population size for each map segment and ateach zoom level. Each location is then assigned a numeric oralphanumeric code or classification based on which population bin towhich it is assigned.

FIG. 20B is a flowchart illustrating one embodiment of a method ofdisplaying location names on a map based on the number of locationswithin the display area. Beginning at block 2050, elements, e.g.,streets, highways, highway shields, coastline, water features, etc. ofthe selected map segments are displayed with the desired map center andzoom level. Next at block 2052, the mapping application module 202counts the number of locations names in each bin for the currentlydisplayed screen area, based on the numeric or alphanumeric codeassigned to each location. Next at block 2054, the mapping applicationmodule 202 iterates through the municipality size bins from the largestto the smallest population bins, to display the location names Atdecision block 2056, the total number of location names within thecurrently displayed location population bin for all the map segmentscurrently being displayed, is compared to a predetermined number ofallowable location names to be displayed for that zoom level. If thethreshold for the number of allowable location names to be displayed isexceeded, the method proceeds to block 2058, and no more locations aredisplayed on the map. If the threshold is not exceeded, the methodproceeds to block 2060 where the next smaller location name bin isselected. The method then returns to block 2054 and continues processingthe remaining location name bins and the location names for display asdiscussed above with reference to block 2054.

FIG. 21 is a flowchart illustrating an embodiment of a method ofproviding a user interface for getting driving directions from thecurrent location. Beginning at block 2110, the user interface module 206is configured to provide a control for accessing directions from thecurrent location to or from a plurality of predetermined locations. Inone embodiment, at least one of the pre-determined locations is adefault home location, such as determined from other data associatedwith a user of the electronic device 100. In another embodiment, a userinterface is provided for selecting a location from any pushpin datastored on the device. In one embodiment, one or more selected locationsare selected and stored as a predefined “preferred” locations (e.g., a“home” and a “work” location). In one embodiment, the control is a menuor other user interface control associated with a pushpin or otherlocation on a displayed map. In another embodiment, the control is amenu or task bar button. Next at block 2120, the user interface module206 determines that the control has been activated. Moving to block2120, the mapping application module 202 receives the direction requestand determines the current location of the electronic device 100. In oneembodiment, the mapping application module 202 communicates with a GPSdevice to determine the current location. In another embodiment, themapping application module 202 determines the current device locationbased on position information received from the wireless mobilecommunications network 220. Next at block 2140, the mapping applicationmodule 202 determines driving directions to/from the current positionand the selected position and presents those directions through the userinterface module 206.

Another embodiment includes a method of identifying pushpin data fromtext presented in any application on the device 100. In one embodiment,this functionality is integrated with the system 200 and the geocodingengine module 208 used to associate geographic coordinates orpseudo-coordinates with any pushpins so identified. Associatingcoordinate or pseudo-coordinate data with pushpins identified fromtextual addresses or other information produces pushpin data that can bedisplayed on a map without further processing. This is desirable toallow efficient display of pushpins without having to look up, forexample, the coordinates of a large database of pushpins at displaytime˜. Moreover, such pushpins can be displayed on the electronic device100 even when the device 100 does not include a full map database forgeocoding addresses or is out of communication with the network 200.

FIG. 22 is a flowchart illustrating one embodiment of a method forcreating a geocoded pushpin from text identified as containing anaddress. Beginning at block 2210, an address is identified such as anaddress in a block of text. In one embodiment, the API module 210 isconfigured to interface with any other application or data source 211 onthe electronic device 100 so as to provide an interface forautomatically identifying an address, or allowing a user to manuallyidentifying an address. In one embodiment, the data source 211 includesthe smart tag feature of Microsoft Corporation's Office products. Insuch an embodiment, the API module 210 is configured to receiveaddresses identified by the smart tag software. Next at block 2220, theother application communicates the identified address, e.g., via the APImodule 210, to the mapping application module 202. Moving to block 2230,the mapping application module 202 parses the identified address, orconverts the address into an appropriate pushpin format if the addresshas been parsed by the data source 211. Next at block 2240, the mappingapplication module 202 requests geocoding of the data by the geocodingengine module 208 or by a geocoding engine located on an intermediateserver 240. By including geographic location data in the pushpin, theelectronic device 100 can later use that data to display the pushpincorrectly on a map even when the electronic device 100 does not include,or is not in contact with, a geocoding database. Thus, pushpin data canbe shared between devices and displayed on a map by any other electronicdevice 100 regardless of whether the other electronic devices alsoinclude the geocoding engine module 208. In addition, the pushpin datawith geographic location attached can be more efficiently processedlater because addresses are not repeatedly geocoded each time thepushpin data is used or queried.

Moving to block 2250, the mapping application module 202 creates apushpin including the geographic location data from the geocoding enginemodule 208. Next at block 2260, the mapping application module 202stores the pushpin and its associated coordinate or pseudo-coordinatedata. In one embodiment, the mapping application module 202 stores thepushpin via the database module 212.

Another embodiment includes a method of manually selecting a map areabased in its display color, rather than the position tapped on thedisplay screen. Electronic devices 100 increasingly include displayshaving higher color or grayscale bit resolution. For example, a 16 bitdisplay can display over 64,000 shades of color. In other embodiments,the display color resolution ranges from 832 bits. Thus, many, if notmost, maps can be created such that each country, region, or other areaon the map can be colored or shaded in a different color. Thus, thisembodiment is a method of efficiently determining which state, country,or other geographic region has been selected by a user based on thecolor of a selected display location. Identifying a map location basedon the displayed color data may be particularly advantageous on devicesthat have limited processing or memory to avoid maintaining additionaldata structures for identifying a selected point with a map region orperforming computationally intensive processing to identify a selectedpoint with a map region.

FIG. 23A is a flowchart illustrating one embodiment of a method ofpreparing such a map. Beginning at block 2310, a map of a selected areais created. Next at block 2310, each state, country, region or otherarea in the map is associated with a different color. In one embodiment,these colors are visually very close, e.g., one or two bits differentfrom at least one other color. FIG. 23B is a flowchart illustrating oneembodiment of a method of identifying a selected region using adisplayed map such as created using the method of FIG. 23A. Beginning atblock 2320, the user interface module 206 receives a control inputassociated with a particular location such as a pixel on a displayedmap, e.g., from a mouse click or a stylus tap on a touchscreen, etc. Theuser interface module 206 determines the color of the selected location.Next at block 2322, the mapping application module 202 identifies one ormore map items, such as state, province, county, or township name,associated with the region that is assigned the color of the selectedlocation. Moving at block 2324, the user interface module 206 providesoptions for using the identified map items, such as selecting amunicipality within the region selected. For example, in one embodiment,the preferred region interface discussed with reference to FIGS. 19A-19Cis invoked.

FIG. 24 is a flowchart illustrating an exemplary method 2400 ofpre-caching data in a system such as the system 200. The method 2400begins at a block 2402 in which the system 200 determines the locationof the electronic device 100 via a location determination component suchas the GPS 120. Next at a block 2404, the system 200 stores the positionin a log. In one embodiment, the log is limited to a predeterminednumber of positions or to positions within a predetermined period oftime. Next at a block 2406, the mapping application module 202 predictsthe heading of the electronic device. In another embodiment, theprediction is based on the current heading determined by the GPS 120. Inanother embodiment, the prediction is based on a current location andthe log of past locations. In one such embodiment, the mappingapplication module 202 averages the current position with the average oftwo or more previous positions

Next at a block 2410, the mapping application module 202 identifies mapsegments along the heading that are not stored on the electronic device100. In one embodiment, the mapping application module 202 determines avector based on • the electronic devices heading and increases thelength of the vector incrementally until it projects from the currentlocation to a position for which the electronic device 100 lacks mapdata. In one embodiment, the increment of the vector length increase isbased on the zoom level of the map. In one embodiment, the increment isabout equal to size (e.g., width) of each map data segment at thecurrent zoom level. Next at a block 2412, the mapping application module202 downloads the identified map segments. In one embodiment, the numberof identified map segments that are downloaded is reduced to a numberthat fits within the storage space of the electronic device. In anotherembodiment, the identified map segments are downloaded and may replaceexisting map segments in storage according to, in one embodiment, acache replacement algorithm such as described with reference to FIG. 13.

Moving to a block 2414, the mapping application module 202 may alsodownload geographically referenced contents such as points of interestor pushpins associated with the newly identified and downloaded mapsegments. In one embodiment, the points of interest are selected basedon user preferences for data to be downloaded upon entering a new area.The points of interest data may include data such as traffic data,traffic incident data, or weather conditions in the newly identified mapdata segments. The method 2400 thus allows a device to preload map datathat is likely to be needed so as to avoid download delays when the datais needed. In addition, this preloaded data may be downloaded when theelectronic device 100 is in communication with map data managementserver 230 so that it is available even if the device 100 moves out ofnetwork communication. In one embodiment, the downloaded data is deletedwhen, for example, the predicted heading changes, or the device hasmoved beyond the corresponding map location along the route.

FIG. 25 is a flowchart illustrating another exemplary method 2500 ofpre-caching data in a system such as the system 200. The method 2500begins at a block 2502 in which the mapping application module 202determines, or receives, a route to a particular location. In oneembodiment, the system 200 provides interactive guidance for followingthe route. Next at a block 2504, the mapping application module 202identifies map segments along the route that are not stored on theelectronic device. Moving to a block 2506, the mapping applicationmodule downloads the identified map segments. In one embodiment, thedownloading is limited by available storage on the device 100. Inanother embodiment, the downloaded data replaces existing data on thedevice according to a cache or storage management policy such asillustrated with reference to FIG. 14. In one embodiment,

Depending on the embodiment, the acts or events of the exemplary methodsillustrated herein can be performed in different sequences, can bemerged, or can be left out altogether. (e.g., not all acts or events arenecessary for the practice of the method), unless the text specificallyand clearly states otherwise. In addition, the methods described hereincan include additional acts or events unless the text specifically andclearly states otherwise. Moreover, unless clearly stated otherwise,acts or events may be performed concurrently, e.g., through interruptprocessing or multiple processors, rather than sequentially. In oneembodiment, the mapping application module 202 may also download pointsof interest or pushpins associated with the newly identified anddownloaded map segments.

While the above detailed description has shown, described, and pointedout novel features of the invention as applied to various embodiments,it will be understood that various omissions, substitutions, and changesin the form and details of the device or process illustrated may be madeby those skilled in the art without departing from the spirit of theinvention. As will be recognized, the present invention may be embodiedwithin a form that does not provide all of the features and benefits setforth herein, as some features may be used or practiced separately fromothers.

Clearly, other embodiments and modifications of this invention willoccur readily to those of ordinary skill in the art in view of theseteachings. The above description is illustrative and not restrictive.This invention is to be limited only by the following claims, whichinclude all such embodiments and modifications when viewed inconjunction with the above specification and accompanying drawings. Thescope of the invention should, therefore, be determined not withreference to the above description, but instead should be determinedwith reference to the appended claims along with their full scope ofequivalents.

What is claimed is:
 1. A method of downloading pushpin data, comprising:receiving, from an electronic network, an indication of a currentsegment for geographically related data, the current segment comprisinggeographically related data for a current location of a device, thecurrent segment corresponding to a portion of geographically relatedcontent displayed on the device; receiving pushpin criteria for thedevice; identifying pushpin data based on the current segment and thepushpin criteria, the pushpin data indicating a pushpin location; andtransmitting, on the electronic network, the pushpin data.
 2. The methodof claim 1, further comprising receiving a current segment index,wherein the current segment index indicates the current segment.
 3. Themethod of claim 1, wherein the pushpin data indicates a plurality ofpushpin locations.
 4. The method of claim 1, further comprising:receiving, from the electronic network, an indication of a new currentsegment, the new current segment comprising geographically related datafor an updated current location of the device, the new current segmentcorresponding to a portion of geographically related content displayedon the device; identifying new pushpin data based on the new currentsegment and the criteria, the new pushpin data indicating a secondpushpin location; and transmitting, on the electronic network, the newpushpin data.
 5. A method of downloading pushpin data, comprising:displaying, by a device, a current segment of geographically relateddata, the current segment including geographically related data for acurrent location of the device and for a portion of geographicallyrelated content displayed on the device; transmitting, to a seconddevice, an indication of the current location; transmitting, to thesecond device, an indication of criteria for pushpin data; receiving,from the second device, pushpin data, the pushpin data indicating atleast one pushpin location and meeting the criteria; and displaying, bythe device, pushpin information on a display based on the receivedpushpin data.
 6. The method of claim 5, wherein the received pushpindata comprises a plurality of pushpin locations and correspondinggeographical pushpin indexes, and display of the pushpin information isfurther based on the geographical pushpin indexes.
 7. The method ofclaim 6, wherein the geographically related content displayed on thedevice is formed by a plurality of rectangular segments, wherein theplurality of rectangular segments comprises the current segment.
 8. Themethod of claim 7, wherein only pushpin locations that have geographicalpushpin indexes corresponding to one of the plurality of rectangularsegments are displayed.
 9. The method of claim 8, wherein only pushpinlocations that have geographical pushpin indexes equal to an index ofone of the plurality of rectangular segments are displayed.
 10. Themethod of claim 8, further comprising determining the geographicalpushpin indexes based on the received pushpin data.
 11. The method ofclaim 5, further comprising applying a second criteria to the receivedpushpin data, wherein the displayed pushpin data meets the secondcriteria.
 12. The method of claim 11, wherein application of the secondcriteria selects pushpins from the pushpin data with particular layeridentifiers.
 13. An apparatus for downloading pushpin data, comprisingone or more processors configured to: receive, from an electronicnetwork, an indication of a current segment, the current segmentcomprising geographically related data for a current location of adevice, the current segment corresponding to a portion of geographicallyrelated content displayed on the device; receive pushpin criteria forthe device; identify pushpin data based on the current segment and thepushpin criteria, the pushpin data indicating a pushpin location; andtransmit, on the electronic network, the pushpin data.
 14. The apparatusof claim 13, wherein the one or more processors are configured toreceive a current segment index, wherein the current segment indexindicates the current segment.
 15. The apparatus of claim 13, whereinthe pushpin data indicates a plurality of pushpin locations.
 16. Theapparatus of claim 13, wherein the one or more processors are furtherconfigured to: receive, from the electronic network, an indication of anew current segment, the new current segment comprising geographicallyrelated data for an updated current location of the device, the newcurrent segment corresponding to a portion of geographically relatedcontent displayed on the device; identify new pushpin data based on thenew current segment and the criteria, the new pushpin data indicating asecond pushpin location; and transmit, on the electronic network, thenew pushpin data.
 17. A first device for downloading pushpin data,comprising: an electronic display; one or more processors configured to:display a current segment, the current segment including geographicallyrelated data for a current location of the first device and for aportion of geographically related content displayed on the electronicdisplay, transmit, to a second device, an indication of the currentsegment, transmit, to the second device, an indication of criteria forpushpin data, receive, from the second device, pushpin data, the pushpindata indicating at least one pushpin location and meeting the criteria,and display pushpin information on the display based on the receivedpushpin data.
 18. The device of claim 17, wherein the received pushpindata comprises a plurality of pushpin locations and correspondinggeographical pushpin indexes, and the one or more processors are furtherconfigured to display the pushpin information further based on thegeographical pushpin indexes.
 19. The device of claim 17 wherein the oneor more processors are further configured to form geographically relatedcontent on the electronic display using a plurality of rectangularsegments, wherein the plurality of rectangular segments comprises thecurrent segment.
 20. The device of claim 19, wherein the one or moreprocessors are configured to display only pushpin locations that havegeographical pushpin indexes corresponding to one of the plurality ofrectangular segments.
 21. The device of claim 20, wherein the one ormore processors are configured to only display pushpin locations thathave geographical pushpin indexes equal to an index of one of theplurality of rectangular segments.
 22. The device of claim 20, whereinthe one or more processors are further configured to determine thegeographical pushpin indexes based on the received pushpin data.
 23. Thedevice of claim 17, wherein the one or more processors are configured toapply a second criteria to the received pushpin data, and are furtherconfigured to display pushpin data meeting the second criteria.
 24. Thedevice of claim 23, wherein application of the second criteria selectspushpins from the pushpin data with particular layer identifiers.